Media library monitoring system and method

ABSTRACT

Embodiments of methods and systems comprise collecting data associated with a library or library components and storing the collected data in repository. By collecting data associated with a library or library components and storing the collected data in a repository, the degradation of library components can be monitored and the reliability of library components determined, allowing unreliable components to be bypassed or replaced, enhancing the reliability of the library and preventing data loss.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims a benefit of priorityunder 35 U.S.C. 120 of the filing date of U.S. patent application Ser.No. 13/430,429 by inventor Sims, entitled “Media Library MonitoringSystem and Method” filed Mar. 26, 2012, and U.S. patent application Ser.No. 13/459,720 by inventor Sims, entitled “Media Library MonitoringSystem and Method” filed Mar. 30, 2012, which are hereby fullyincorporated by reference, and are continuations of, and claim benefitof priority under 35 U.S.C. 120 to the filing date of U.S. patentapplication Ser. No. 12/692,403 by inventors Moody et al., entitled“System and Method for Identifying Failing Drives or Media in MediaLibrary” filed Jan. 22, 2010, which is fully incorporated herein byreference and which is a continuation-in-part of and claims the benefitof priority of U.S. patent application Ser. No. 12/024,755 by inventorSims, entitled “Media Library Monitoring System and Method” filed Feb.1, 2008, issued as U.S. Pat. No. 7,908,366 on Mar. 15, 2011, which ishereby fully incorporated by reference herein.

TECHNICAL FIELD

This disclosure describes various embodiments of methods and systems formonitoring a media library. More particularly, embodiments includemethods and systems for collecting data associated with librarycomponents and storing the collected data in a repository.

BACKGROUND

Data represents a significant asset for many entities. Consequently,data loss, whether accidental or caused by malicious activity, can becostly in terms of wasted manpower, loss of goodwill from customers,loss of time and potential legal liability. To ensure proper protectionof data for business and legal purposes, many entities back up data to aphysical storage media such as magnetic tapes or optical disks.Traditionally, backup would occur at each machine controlled by anentity. As the sophistication of network technology increased, manyentities turned to enterprise level backup in which data from multiplemachines on a network is backed up to a remote library. Typically, alibrary includes a variety of components which include a plurality ofmedia for data storage, such as, for example, multiple magnetic tapes.Centralized data backup has the advantage of increased volume,efficiency and redundancy.

In many systems, the data to be backed up and backup commands are sentover a network from multiple machines on the network to a library. Inmany instances, the data to be backed up and the backup commands arerouted to the library through a switch.

One example of a library commonly used in enterprise backup systems is amagnetic tape library. A magnetic tape library can comprise componentssuch as tape cartridges (containing magnetic tape), robots, tape slotsand tape drives. A typical magnetic tape library contains multiplecartridge slots in which tape cartridges can be stored. Tape cartridges,commonly referred to as tapes, are physically moved between cartridgeslots and tape drives by a robot. The robot is controlled by commandsreceived from the host devices on the network. When specific data isrequired, a host device determines which cartridge slot contains thetape cartridge that holds the desired data. The host device thentransmits a move-element command to the robot and the robot moves thetape cartridge to a tape drive which reads the desired data from thetape cartridge.

In a SCSI tape library, devices that are part of the library aretypically addressed by target number. Thus, each drive and robot of atape library typically has a target number. Cartridge slots, on theother hand, are addressed by element numbers that are used by the robotto locate the slots. Because the robot also places tape cartridges inthe drives, each drive is also associated with an element number.

Components of a library are subject to wear and other forms ofdegradation. The degradation of library components can deleteriouslyaffect the reliability of the library.

SUMMARY

Embodiments of methods and systems regard monitoring a library orcomponents of the library. A method for monitoring a library or librarycomponents may comprise collecting data, wherein collecting datacomprises querying a library component at intervals and receivingreturned data, and storing the collected data in a repository. Thecollected data may be formatted into structures and arranged in an orderin the repository. The data in the repository may be accessed anddisplayed to a user using a user interface.

Embodiments of methods and systems for monitoring a library orcomponents of the library can include a system comprising a controllerand a set of computer instructions executable by the controller toimplement the above-described method. Other embodiments may include asoftware product comprising computer instructions executable toimplement the above-described method. In a further embodiment, computerreadable media may contain computer instructions operable to implementthe above-described method.

Embodiments of the above methods and systems allow for the non-intrusivecollection of data associated with a library or library components in arepository such that the data can be analyzed by a user and the libraryand components of the library can be monitored over time. For example,data in the repository can be analyzed to monitor the utilization oflibrary components over time to determine if library components arebeing over- or under-utilized. As a specific example, data collected inthe repository can be analyzed to determine if individual drives of thelibrary are being over- or under-utilized. Over-utilizing an individualdrive may increase library backup time and may cause excessive wear onthe over-utilized drive or on components associated with theover-utilized drive.

BRIEF DESCRIPTION OF THE FIGURES

A more complete understanding of embodiments of methods and systems andthe advantages thereof may be acquired by referring to the followingdescription, taken in conjunction with the accompanying drawings inwhich like reference numbers indicate like features and wherein:

FIG. 1 is a diagrammatic representation of one embodiment of a library;

FIGS. 2A, 2B, and 2C are diagrammatic representations of embodiments ofexample network topologies comprising a library and a monitoringappliance;

FIG. 3 is a flowchart of one embodiment of a method for collecting orstoring data;

FIG. 4 is a flowchart of a method for tracking tape movements;

FIG. 5 depicts an XML representation of one embodiment of a datastructure;

FIGS. 6A and 6B (FIG. 6) depicts an XML representation of one embodimentof a data structure;

FIG. 7 depicts XML representations of embodiments of data structures;

FIG. 8 is one example of a block diagram of a system for collecting orstoring data;

FIG. 9 is a block diagram of one example of a controller operable tocollect or store data;

FIG. 10 is one example of a graphical user interface for displayingdata;

FIG. 11 is one example of a graphical user interface for displayingdata;

FIG. 12 is one example of a graphical user interface for displayingdata;

FIG. 13 is one example of a graphical user interface for displayingdata;

FIG. 14 is one example of a graphical user interface for displayingdata; and

FIG. 15 is one example of a graphical user interface for displayingdata.

DETAILED DESCRIPTION

Embodiments of systems and methods for library monitoring areillustrated in the FIGURES, like numerals being used to refer to likeand corresponding parts of the various drawings.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a product,process, article, or apparatus that comprises a list of elements is notnecessarily limited only those elements but may include other elementsnot expressly listed or inherent to such product, process, article, orapparatus. Further, unless expressly stated to the contrary, “or” refersto an inclusive or and not to an exclusive “or.” For example, acondition A or B is satisfied by any one of the following: A is true (orpresent) and B is false (or not present), A is false (or not present)and B is true (or present), and both A and B are true (or present).

Additionally, any examples or illustrations given herein are not to beregarded in any way as restrictions on, limits to, or expressdefinitions of, any term or terms with which they are utilized. Insteadthese examples or illustrations are to be regarded as being describedwith respect to one particular embodiment and as illustrative only.Those of ordinary skill in the art will appreciate that any term orterms with which these examples or illustrations are utilized willencompass other embodiments which may or may not be given therewith orelsewhere in the specification and all such embodiments are intended tobe included within the scope of that term or terms. Language designatingsuch nonlimiting examples and illustrations includes, but is not limitedto: “for example”, “for instance”, “e.g.”, “in one embodiment”.

Media library monitoring systems can collect data associated with amedia library and components of the media library. Data may be collectedover time and stored in the repository such that the repository containsdata associated with individual library components such as, for example,drives, media changers or other library components. Because therepository contains data associated with different library componentsand because the data in the repository extends over time, the data inthe repository may be organized such that the data is organized withrespect to time and with respect to the individual library components oraccording to other parameters.

A user interface may be used to display the collected and organized datato a user and the user may select data to view utilizing the userinterface. Thus, collecting data in a repository over time andorganizing the data allows a library and individual library componentsto be monitored and problems with the library or library components tobe identified and rectified, for example, by allowing unreliable orunacceptably degraded components to be identified and bypassed orreplaced, thereby enhancing the reliability of the library andproactively preventing data loss.

FIG. 1 is a diagrammatic representation of one embodiment of a medialibrary, in this example, a tape library. Library 100 can comprisedrives 140 a-140 e, media changer 125 and associated robot 130,import/export element(s) 145 and slots 135 a-135 j. Drives 140 a-140 ecan read/write data from/to magnetic tape (contained within cartridges),eject tape cartridges and perform other operations. Slots 135 a-135 jstore the magnetic tape cartridges when they are not in a drive androbot 130 moves the magnetic tape cartridges between drives 140 a-140 eand slots 135 a-135 j. For example, robot 130 may move a tape cartridgestored at slot 135 a to drive 140 b so that data can be written to thetape cartridge. It should be noted that libraries may employ a singlerobot or multiple robots in an expandable or modular configuration.

To collect data associated with a library or library components, amonitoring appliance can query a library or library components over anetwork utilizing commands. In response to received commands, thelibrary or library components may return data associated with aparticular command to the monitoring appliance. In one embodiment, amonitoring appliance can query a library over a network utilizing SCSIcommands such as the Read Element Status command, Log Sense Command,Inquiry Command and other commands.

A Read Element Status (RES) command is a command which is used to querythe state of a library. A RES command is sent to a media changer and inresponse, the media changer returns data associated with the library orthe media changer. Such data may include the locations of individualtape cartridges. Thus a RES command provides a snapshot of a library atany one time. Examples of a RES command can be found in “SCSI MediaChanger Commands-2 (SMC-2)”, (INCITS T10 Project 1383D), Revision 7,Nov. 18, 2003, propagated by the T10 Technical Committee of theInterNational Committee on Information Technology Standards (INCITS),which is hereby incorporated by reference.

A Log Sense (LS) command is a command which is used to obtain dataassociated with a particular drive. A LS command is sent to a particulardrive of a library and in response, the drive returns data associatedwith the drive and/or the media contained in the drive depending on theactual LS command. For example, such data might include: read errors,write errors, utilization and performance data, data regarding the datawritten and read to a media, media loaded, detail tables or other data.In one embodiment, the amount of data written over a period of time maybe derived from data returned in response to one or more LS commands.More specifically, data returned in response to an LS command mayinclude Log Sense page 0×C, 0×32 or 0×39 which may include data fromwhich the amount of data written by a particular drive over a period oftime may be derived. In one embodiment, deriving the amount of datawritten by a particular drive over a period of time may comprise one ormore calculations. Examples of a LS command can be found in “SCSIPrimary Commands-3 (SPC-3)”, (Project T10/1416-D), Revision 22a, Mar.25, 2005, propagated by the T10 Technical Committee of the InterNationalCommittee on Information Technology Standards (INCITS), which is herebyincorporated by reference.

An Inquiry command is a command that is used to query relatively staticinformation (which may include, for example, serial number, manufactureror other relatively static information) from components of a librarysuch as a drive or a media changer. According to one embodiment, Inquirycommands are used to query individual library components. That is, anindividual Inquiry command may query a particular library component.Examples of an Inquiry command can be found in “SCSI Primary Commands-3(SPC-3)”, (Project T10/1416-D), Revision 22a, Mar. 25, 2005, propagatedby the T10 Technical Committee of the InterNational Committee onInformation Technology Standards (INCITS), referenced above.

Methods and systems for collecting data from a library or librarycomponents can utilize a monitoring appliance which can be a Read VerifyAppliance (RVA). The monitoring appliance queries a library or librarycomponents over time by sending RES, LS, Inquiry commands and/or othercommands to the library or library components at intervals. Datareturned in response to the commands is collected in a repository suchthat the repository may contain data associated with a plurality oflibrary components of a library. For example, the repository may containdata regarding all the drives in a library. Data within the repositorymay be organized to allow a user to monitor various library components.For example, data may be organized in a chronological order so that auser can monitor the incidence of errors (for example, soft and hardread or write errors) over time. The data may further be organized suchthat superfluous data is removed. For example, redundant data might notbe displayed to a user or might be purged from the repository. Likewise,unnecessary data or data that the system is configured not to monitormight be purged from the repository or not saved to the repository inthe first place.

FIG. 2A is a diagrammatic representation of a system 200 a in which aplurality of hosts 202 a-202 d have access to library 100 over network205. Network 205 can comprise the Internet, a SAN, a LAN, a WAN, awireless network or any other communications network known in the art.Hosts 202 a-202 d are coupled to library 100 via network 205 and switch207. Similarly, library 100 can communicate with switch 207 over anysuitable communications link or network known in the art and can useadditional protocols such as iSCSI, TCP/IP, or other protocol known inthe art. Monitoring appliance 220 is coupled to switch 207 such that itcan send commands to library 100 or library components of library 100.

Switch 207 is connected to library 100. Thus switch 207 can forwardcommands (such as, for example, RES, LS or Inquiry commands) frommonitoring appliance 220 to library 100. Switch 207 receives datagenerated in response to the commands from library 100 and forwards thedata to monitoring appliance 220 which collects the data in arepository. Thus monitoring appliance 220 can continually query library100 and components of library 100 for data which can be stored in arepository, allowing a user to monitor the components of library 100.Because monitoring appliance 220 collects data by sending commands to alibrary, monitoring appliance 220 does not need to intercept commands orresponses from network 205 to obtain data associated with a library orlibrary components. Thus, in one embodiment, monitoring appliance 220can be an out-of-band appliance. This allows monitoring appliance 220 tobe a non-intrusive device which does not monitor or interfere withcommands from and responses to hosts 202 a-202 d. Consequently,monitoring appliance 220 can be a compartmentalized device which can beconnected to a switch and which does not have to be integrated intonetwork 205. An advantage of this out-of-band methodology is that amonitoring appliance can be used to monitor library components withoutcumbersome configuring.

While a particular network topology is shown in FIG. 2A, a monitoringappliance may be used in other network topologies to collect dataassociated with a library or library components. FIGS. 2B and 2C arediagrammatic representations of example network topologies in which amonitoring appliance can be used to collect data associated with alibrary or components of the library.

For example, FIG. 2B is a diagrammatic representation of a system 200 bhaving a network topology in which monitoring appliance 220 is coupledto media changer 125 and coupled to drives 140 a-140 e through switch207. Thus, monitoring appliance 220 can communicate with (by, forexample, sending commands to or receiving data from) media changer 125and drives 140 a-140 e. By way of further example, FIG. 2C is adiagrammatic representation of a system 200 c having a network topologyin which monitoring appliance 220 is coupled to drives 140 a-140 ethrough switch 207 and is coupled to media changer 125 through network209. Thus, monitoring appliance 220 can communicate with media changer125 and drives 140 a-140 e. In system 200 c, networks 205 and 209 can bedifferent types of networks. For example, network 205 might be a fibrechannel network whereas network 209 might be a IP network. It should benoted, however, that the topologies of systems 200 a, 200 b and 200 care provided by way of example and not limitation.

While shown as a physical media library in FIG. 2A-2C, library 100 canbe a virtual media library that is a virtual representation of one ormore physical media libraries as presented by switch 207, a librarycontroller or other component. Examples of library virtualization aredescribed in U.S. patent application Ser. No. 10/704,265, entitled“System and Method for Controlling Access to Multiple Physical MediaLibraries,”and U.S. patent application Ser. No. 10/703,965, entitled“System and Method for Controlling Access to Media Libraries,” both ofwhich are hereby incorporated by reference herein.

FIG. 3 is a flow chart illustrating one embodiment of a method forcollecting data and organizing the collected data so that it can beaccessed by or displayed to a user. According to one embodiment, themethod of FIG. 3 can be implemented as a set of computer executableinstructions stored on a computer readable medium at, for example,monitoring appliance 220. The set of computer executable instructionscan, when executed, collect data associated with library components in anon-intrusive manner. At collect data step 310, data is collected by amonitoring appliance by querying library components of a library fordata by sending commands corresponding to the library components to thelibrary components. In response, the library components return dataassociated with the library components. More specifically, in oneembodiment, RES, LS and Inquiry commands are sent to library componentsand, in response, the library components return corresponding data. Datamay be collected over time by collecting data from library components atintervals. For example, various commands can be sent every 10 seconds,every 20 seconds or with any other frequency. Thus, over time, librarycomponents may be queried a plurality of times, and as a result, therepository may contain data regarding library components at differentpoints in time.

The monitoring appliance, at compile data step 320, can compile thereturned data. For example, the monitoring appliance can compile thedata in defined structures which, in one embodiment, may include XMLstructures or other structures or equivalents. A structure may containdata associated with a library component returned in response to one ormore commands (such as, for example, RES, LS or Inquiry commands). Forexample, a XML structure can include data from RES commands and serialnumbers of library components determined from Inquiry commands issued tocorresponding library components. At store data step 330, the monitoringappliance stores the returned data in a repository. Storing data in arepository may comprise storing structures in the repository or maycomprise unpacking returned data compiled at compile step 320 andstoring the data in the repository. In one embodiment, the data may bestored in records in a database at the repository.

At organize data step 340, the data in the repository is organized. Aspart of step 340, data in the repository can be arranged inchronological order and/or superfluous or redundant data can be purged.Corresponding data can be grouped together. For example, data structurescorresponding to a particular drive may be arranged in chronologicalorder within the repository.

At process data step 350, data in the repository may be processed todisplay desired data to a user. For example, a user may only want to seedata corresponding to a particular library component. At process datastep 350, the data in the repository is processed such that the desireddata is selected to be displayed to a user. Similarly, data may beprocessed into graphs or charts, or in accordance with any number ofpurposes or user desires.

In one embodiment, processing data in the repository can comprisecomparing returned library states or data regarding the locations ofindividual tape cartridges stored in the repository to track themovement of one or more tape cartridges. For example, data in therepository corresponding to different times can be compared and themovement of tape cartridges in a library tracked by differencing thelocations of tape cartridges in a library at different times. Inembodiments in which data is stored in records in a database, recordsassociated with different times may be compared to track the movement oftape cartridges. Processing data can further comprise correlating errorswith a particular library component based on the movement of one or moretape cartridges within the library.

FIG. 4 is a flow chart illustrating one embodiment of a method fortracking the movement of one or more tape cartridges which can beimplemented as part of process data step 350 of FIG. 3. According to oneembodiment, the method of FIG. 4 can be implemented as a set of computerexecutable instructions stored on a computer readable medium at, forexample, monitoring appliance 220. At step 460, data which may be, forexample, data contained in structures or database records associatedwith different times may be compared. Based on comparisons between data,tape movements within the library can be tracked (step 465). Forexample, if in one structure or record associated with a time, a tapewas at a specified drive in the library and in another structure orrecord corresponding to a subsequent time, the same tape is in a slot,it can be determined that the tape has been moved from the drive to theslot. Based on such comparisons between data in the repository, themovement of tapes within a library can be tracked over time. At step470, errors may be correlated with library components based on tapemovements. This allows the monitoring appliance to monitor thedegeneration of library components. For example, if a drive registers anincreasing number of errors, regardless of the robot or tape used withthe drive, then the drive is likely degenerating and becomingincreasingly unreliable. Accordingly, this allows the failing drive tobe identified and bypassed or replaced before it causes data loss orlibrary failure. While the method shown in FIG. 4 is described in thecontext of process data step 350 of FIG. 3, the method of FIG. 4 may beimplemented as part of other steps, for example, as part of organizedata step 340.

As described above, tracking the movement of tape cartridges or othermedia allows sources of errors to be identified. For example, a tapecartridge may encounter errors when used with a tape drive A but mayencounter no errors when used with other tape drives. If other tapecartridges encounter errors when used with tape drive A, but encounterno errors when used with other tape drives, this implies that tape driveA is unreliable. Accordingly, tape drive A may be bypassed or replaced.Thus, by tracking the movement of one or more tape cartridges, errorscan be correlated to a particular tape or drive. Tracking cartridges ina library and correlating data (such as, for example, errors or otherdata) with cartridges or drives is described in U.S. patent applicationSer. No. 11/801,809, entitled “Method and System for Non-IntrusiveMonitoring of Library Components,” which is hereby incorporated byreference.

Returning to FIG. 3, the above method or steps of the above method setforth in FIG. 3 may be repeated at intervals over time such that therepository contains data associated with the library and components ofthe library over a period of time. For example, data associated with alibrary may be continually collected and compiled over time (steps 310and 320). The period of time may be of any length, for example, days,weeks, months, years or any other length of time.

FIG. 5 is an example XML representation of a data structure containingdata returned in response to an Inquiry command and a LS command. Thedata in the data structure may be stored in a repository along with datafrom multiple similar data structures containing data collected atdifferent points in time, and the data may be organized in achronological or other order in the repository. More specifically, inone embodiment, data may be unpacked from the data structure and storedin the repository. In a further embodiment, data may be stored inrecords in a database contained in the repository.

FIG. 6 is an example XML representation of a data structure containingdata returned in response to an Inquiry command and a RES command. Thedata in the data structure may be stored in a repository along with datafrom multiple similar data structures containing data collected atdifferent points in time, and the data may be organized in achronological or other order in the repository. More specifically, inone embodiment, data may be unpacked from the data structure and storedin the repository. In a further embodiment, data may be stored inrecords in a database contained in the repository.

FIG. 7 is an example comparison of XML representations of structures,for example data structures, containing data returned in response to REScommands issued at different times. Comparing data may allow for themovement of tape cartridges within a library to be tracked. Because aRES command queries the state of a library, each structure in FIG. 7 maycontain data regarding the state of the library, i.e. the location oftapes within the library at different times. Structure 510 contains dataassociated with a time. Structure 520 contains data associated with asubsequent time. By comparing the differences in the data, it ispossible to determine that the tape with volume identity 000105 hasmoved from the slot at element identity 0×1007 to the drive at elementidentity 0×101. This movement is shown by directional arrow 530.

FIG. 8 is a diagrammatic representation of a system operable to collectdata from a library or library components and store the collected datain a repository where it can be accessed by a user (virtual orotherwise). In FIG. 8, library 610 (which in one embodiment may be, forexample, a library such as library 100 of FIG. 1 or any other library)is coupled to network 620 via switch 630 such that library 610 canreceive commands sent over network 620. Data Engine 640 is also coupledto network 620 such that it can send commands over network 620 andreceive data over network 620. Data engine 640 is coupled to storageengine 650 such that it can forward data to storage engine 650. In turn,storage engine 650 is coupled to repository 660 such that it can storedata in repository 660. Interface engine 670 allows user 680 to accessdata stored in repository 660 utilizing user interface 690. According toone embodiment, data engine 640, storage engine 650, repository 660,interface engine 670 or user interface 690 can be implemented as a setof computer executable instructions stored on a computer readable mediumat, for example, monitoring appliance 220.

Data Engine 640 of FIG. 8 collects data from library 610 by sendingcommands (which in on embodiment may include, for example, RES, LS orInquiry commands) over network 620 to library 610 or library componentsof library 610. In response, library 610 or corresponding librarycomponents return data corresponding to the received commands overnetwork 620 to data engine 640. Data engine 640 receives the data andforwards the collected data to storage engine 650. Storage engine 650stores the data in repository 660. For example, in one embodiment, datareturned in response to an Inquiry command and a LS command may beformatted into a single XML structure at data engine 640 and forwardedto storage engine 650. Storage engine 650 may receive XML structures orother structures containing data, unpack the data and store the data inrepository 660. In a further embodiment, storage engine 650 stores thedata in records contained in a database at repository 660. Through therepetition of the above described process at intervals over time,repository comes to contain data associated with the library andcomponents of the library over a period of time. Data contained inrepository 660 may be organized. Organizing data may include, forexample, organizing data in a chronological or other order or purgingredundant data.

Collecting data associated with a library or library components inrepository 660 and organizing the data allows a user to view the data tomonitor library components. In FIG. 8, user 680 may access data inrepository 660 via interface engine 670 utilizing user interface 690. Inone embodiment, user interface 690 is a graphical user interface (GUI),which allows for a user-friendly display of data contained in repository660. User interface 690 may be capable of displaying desired data touser 680 or displaying data which may be useful in monitoring librarycomponents. For example, user 680 may utilize user interface 690 toselect desired data to display in a graphical form. The desired data maybe data regarding a particular library component of library 610 or dataregarding a particular type of error. Desired data may span a userspecified period. More specifically, user 680 may use user interface 690to display write errors of a particular drive for a day, month, year orany other period. If the write errors increase over time, the drive maybe degrading and may need to be replaced.

While in the above example, data engine 640, storage engine 650,repository 660, interface engine 670 or user interface 690 are describedas being part of a monitoring device, data engine 640, storage engine650, repository 660, interface engine 670 or user interface 690 may becontained in a component that is not physically part of the monitoringappliance. For example, data could be collected and compiled at themonitoring device but stored in memory coupled to the monitoringappliance. In one embodiment, interface engine 670 or user interface 690run on a host computer which is coupled to repository 660 over anetwork. User 680 can access data in repository 660 utilizing interfaceengine 670 or user interface 690 which may be running on the hostcomputer. Thus, a user may access the data in repository 660 over anetwork. Collected and compiled data may be partially stored in themonitoring appliance and partially stored in separate memory. In oneexample, a portion of collected data may be stored in a memory which isa component of data engine 640 or storage engine 650, while a portion ofcollected data may be stored in a memory which is a component ofrepository 660 or interface engine 670. Repository 660 of FIG. 8 mayinclude a database, spreadsheet or other computer program in which datacan be stored. In a network comprising multiple libraries, each librarymay have a corresponding data engine or storage engine which may forwardcollected data to a common repository or monitoring appliance.

It should be noted that the intervals between querying a library orlibrary components can be fixed periods of time or of variable durationor a combination of the two. Individual library components may also bequeried at different intervals: for example, a drive that is beingheavily used may be queried more frequently than a drive which is notbeing used. In one embodiment, the data engine queries a library orlibrary component every 30 seconds. In another embodiment, the timeduration between querying is less than the backup time or the tapemovement time. In further embodiments, the intervals can be determinedby computer algorithm or user input.

It should further be noted that data may be derived from collected dataand stored in the repository or other data storage. More specifically,collected data returned in response to one or more commands may be usedto derive derived data which may be stored in the repository. Derivingderived data may comprise one or more calculations. The derived data maybe organized. For example, derived data may be stored in particularrecords in a database. Examples of derived data may include, forexample, the bits read by a drive over time (which may be, for example,in bits/second), the data transfer rate of a drive or other data.Statistical analysis may be performed on data stored in a repository.For example, statistical analysis may be performed on collected data orderived data and may be used to predict device or cartridge failurebased on read errors or write errors or other data.

FIG. 9 is a diagrammatic representation of a monitoring appliancecontroller 700 (“controller 700”). Controller can include a processor702, such as an Intel Pentium 4 based processor (Intel and Pentium aretrademarks of Intel Corporation of Santa Clara, Calif.), a primarymemory 703 (which may include, for example, RAM, ROM, Flash Memory,EEPROM or other computer readable medium known in the art) and asecondary memory 704 (which may include, for example, a hard drive, diskdrive, optical drive or other computer readable medium known in theart). A memory controller 707 can control access to secondary memory704. Controller 700 can comprise a communications interface 706 (whichmay comprise, for example, fibre channel interface, Ethernet port orother communications interface known in the art) to connect controller700 to, for example, a switch of a network. An I/O controller 712 cancontrol interactions with the switch. Similarly, an I/O controller 714can control interactions over I/O interfaces 708 and 710. Controller 700can include a variety of input devices. Various components of controller700 can be connected by a bus 726.

Secondary memory 704 can store a variety of computer instructions thatinclude, for example, an operating system such as a Windows operatingsystem (Windows is a trademark of Redmond, Wash. based MicrosoftCorporation) and applications that run on the operating system, alongwith a variety of data. More particularly, secondary memory 704 canstore a software program 730 that collects, compiles, stores, organizesor processes data associated with a library or library components.During execution by processor 702, portions of program 730 can be storedin secondary memory 704 and/or primary memory 703.

Because a repository may contain data associated with a library andlibrary components spanning a period, a user may access the data tomonitor the library or library components over a period of time. Forexample, a user may use a user interface to display data associated witha library component for a desired period of time. The data may bedisplayed in a graphical format.

FIGS. 10-15 are examples of representations of data associated with alibrary or library component(s) and contained in a repository. Therepresentations are part of a GUI which may be utilized by a user toaccess and display data stored in a repository. FIG. 10 is one exampleof a graphical representation 800 of data associated with a drive. Morespecifically, graphical representation 800 displays data associated witha particular drive in drive utilization graph 810 and drive performancegraph 820. Drive utilization graph 810 displays the drive utilization ofa drive over a 30 day period. Drive performance graph 820 displays thedrive performance over a 30 day period. Selector 830 can be used toselect the period of time that the data displayed in graphs 810 and 820spans.

FIG. 11 is one example of a graphical representation 900 of dataassociated with a drive. More specifically, graphical representation 900displays data associated with a particular drive in data written graph910 and data read graph 920. Data written graph 910 displays the amountof data written per day over a 30 day period. Data displayed in datawritten graph 910 may be derived from, for example, Log Sense pages 0×C,0×32 or 0×39 returned in response to one or more LS commands. Data readgraph 920 displays the amount of data read per day over a 30 day period.Selector 930 can be used to select the period of time that the datadisplayed in graphs 910 and 920 spans.

FIG. 12 is one example of a graphical representation 1000 of dataassociated with a drive. More specifically, graphical representation1000 displays data associated with a particular drive in hard writeerrors graph 1010 and soft write errors graph 1020. Hard write errorsgraph 1010 displays the occurrence of hard write errors associated withthe drive over a 30 day period. Soft write errors graph 1020 displaysthe occurrence of soft write errors associated with the drive over a 30day period. Selector 1030 can be used to select the period of time thatthe data displayed in graphs 1010 and 1020 spans.

FIG. 13 is one example of a graphical representation 1100 of dataassociated with a drive. More specifically, graphical representation1100 displays data associated with a particular drive in hard readerrors graph 1110 and soft read errors graph 1120. Hard read errorsgraph 1110 displays the occurrence of hard read errors encountered bythe drive over a 30 day period. Soft read errors graph 1120 displays theoccurrence of soft read errors encountered by the drive over a 30 dayperiod. Selector 1130 can be used to select the period of time that thedata displayed in graphs 1110 and 1120 spans.

FIG. 14 is one example of a graphical representation 1200 of dataassociated with a drive. More specifically, graphical representation1200 displays data associated with a particular drive in tape load countgraph 1210. Tape load count graph 1210 displays the number of tape loadsof the drive on a daily basis over a 30 day period. Selector 1220 can beused to select the period of time that the data displayed in graph 1210spans.

FIG. 15 is one example of a graphical representation 1300 of dataassociated with a drive. More specifically, graphical representation1300 displays data associated with a particular drive in drive summary1310 and tapes used list 1320. Drive summary 1310 displays drive datasuch as serial number, firmware version, whether the drive needscleaning, or other drive data. Tapes used list 1320 lists the tapesloaded into the drive over a 30 day period. Selector 1130 can be used toselect the period of time that the data displayed in list 1320 spans.FIGS. 10-15 are provided by way of example, not limitation, and dataassociated with a library or library components may be presented in anynumber of ways. Furthermore, data contained in a repository may beaccessed over a network using a host computer such that a user interfacecontaining data from the repository may be displayed on a displayassociated with the host computer.

Embodiments can also be implemented with respect to libraries of mediaother than magnetic tapes. For example, the library can comprise aplurality of optical disks (i.e., an optical jukebox) or removable harddrives. Other libraries can utilize a combination of different storagemedia such as hard drives, magnetic media or optical media.

While systems and methods been described with reference to particularembodiments, it should be understood that the embodiments areillustrative and that the scope of the invention is not limited to theseembodiments. For example, while embodiments described above have beendescribed with regard to RES, LS and Inquiry commands, this is by way ofillustration and not limitation. In some embodiments, other commands maybe used to collect data associated with a library or library components.Many variations, modifications, additions and improvements to theembodiments described above are possible. It is contemplated that thesevariations, modifications, additions and improvements fall within thescope of the invention as detailed in the following claims.

What is claimed is:
 1. A method of out-of-band monitoring a medialibrary, comprising: performing a collection process to collect datafrom the media library out-of-band from commands and responses betweenhosts and the media library, wherein collecting data comprises queryingone or more library components of the media library at intervals andreceiving returned data, wherein querying one or more library componentscomprises: sending Log Sense (LS) commands to the media library atintervals; and sending Read Element Status (RES) commands to the medialibrary at intervals; storing the collected data in a repository,wherein storing the collected data in the repository comprises storingdata returned in response to the LS commands or the RES commands in therepository, wherein the collected data in the repository spans aplurality of intervals; deriving data from the collected data, whereinderiving data comprises deriving a metric associated with the medialibrary over the plurality of intervals based on data returned inresponse to the LS commands over the plurality of intervals; accessing aset of data in the repository based on one or more specifications; andproviding the set of data based on one or more specifications.
 2. Themethod of claim 1, further comprising forming one or more structurescontaining data returned in response to one or more LS or RES commands.3. The method of claim 1, wherein the set of data comprises the deriveddata.
 4. The method of claim 1, wherein the set of data comprises thecollected data.
 5. The method of claim 4, wherein providing the set ofdata comprises providing the collected data to another system forfurther processing.
 6. The method of claim 1, wherein: querying one ormore library components further comprises sending one or more Inquirycommands to a drive or a media changer of the media library; and storingthe collected data in the repository comprises storing data returned inresponse to the Inquiry commands.
 7. The method of claim 1, wherein:querying one or more library components further comprises sending one ormore additional commands to a drive or a media changer of the medialibrary, wherein the additional commands comprise SCSI commands; andstoring the collected data in the repository comprises storing datareturned in response to the one or more additional commands.
 8. Themethod of claim 1, further comprising organizing the collected data. 9.A system for out-of-band monitoring of a media library comprisingmultiple components, comprising: a data engine coupled to a network andconfigured to perform a collection process to collect data from themedia library out-of-band from commands and responses between hosts andthe media library, wherein the collection process comprises querying oneor more library components of the media library at intervals andreceiving returned data, wherein querying one or more library componentscomprises: sending Log Sense (LS) commands to the media library atintervals; and sending Read Element Status (RES) commands to the medialibrary at intervals; a storage engine configured to: store thecollected data in a repository over a plurality of intervals, whereinstoring the collected data in the repository comprises storing datareturned in response to the LS commands or the RES commands in therepository; and derive data from the collected data, wherein derivingdata comprises deriving a metric associated with the media library overthe plurality of intervals based on data returned in response to the LScommands over the plurality of intervals; an interface engine coupled tothe repository and configured to connect to a communications link to:access a set of data in the repository based on one or morespecifications; and provide the set of data based on one or morespecifications.
 10. The system of claim 9, wherein the storage engine isconfigured to form one or more structures containing data returned inresponse to one or more LS or RES commands.
 11. The system of claim 9,wherein the set of data comprises the derived data.
 12. The system ofclaim 9, wherein the set of data comprises the collected data.
 13. Thesystem of claim 12, wherein providing the set of data comprisesproviding the collected data to another system for further processing.14. The system of claim 9, wherein: querying one or more librarycomponents further comprises sending one or more Inquiry commands to adrive or a media changer of the media library; and storing the collecteddata in the repository comprises storing data returned in response tothe Inquiry commands.
 15. The system of claim 9, wherein: querying oneor more library components further comprises sending one or moreadditional commands to a drive or a media changer of the media library,wherein the additional commands comprise SCSI commands; and storing thecollected data in the repository comprises storing data returned inresponse to the one or more additional commands.
 16. The system of claim9, wherein the interface engine is configured to display data to a uservia a graphical user interface (GUI).
 17. The system of claim 9, whereinthe storage engine is further configured to perform organizing thecollected data.
 18. The system of claim 9, wherein a monitoringapplicance comprises the data engine and the storage engine.